Release 10.1A: OpenEdge Data Management:
Database Administration
Performance Indicators
Displays activity statistics related to performance. Figure 19–44 shows a sample Performance Indicators display.
Figure 19–44: PROMON Performance Indicators display
The Performance Indicators display shows the total number of each type of operation for the sample period (Total), the number of operations per minute (Per Min) the number of operations per second (Per Sec), and the number of operations per transaction (Per Tx). The display shows the following operations:
- Commits — The number of committed transactions.
- Undos — The number of transactions that were rolled back.
- Index Operations — The total of all operations performed on indexes (for example, index additions and deletions).
- Record Operations — The total of all operations on records (for example, record additions and deletions).
- Total o/s i/o — The total number of read and write operations performed.
- Total o/s reads — The total number of read operations performed.
- Total o/s writes — The total number of write operations performed.
- Background o/s writes — The total number of writes performed by background writers (APWs, BIW, and AIW). For more information on background writers, see Chapter 13, " Managing Performance."
- Partial log writes — Writes to the BI file made before the BI buffer is full. This might happen if:
- The Delayed BI File Write (-
Mf) parameter timer expired before the buffer was filled.- An APW attempts to write a block whose changes are recorded in a BI buffer that has not been written. Because BI notes must be flushed before the AI note is flushed, the AIW writes the data in the BI buffer before the buffer is full so it can do the AI write.
- An AIW ran ahead of the BIW. Because BI notes must be flushed before the AI notes can be written, the AIW writes the BI buffer before it is full, so it can do the AI write.
- Database extends — The total number of times the database was made larger by allocating operating system blocks.
- Total waits — The total number of waits.
- Lock waits — The number of times the database engine waited for a lock to be released.
- Resource waits — The number of times the database engine waited for a resource, such as a row lock, a buffered lock in shared memory, or a transaction end lock, to become available.
- Buffer pool hit rate — The percentage of times that the database engine found a record in the buffer pool and did not have to read the record from disk.
|
Copyright © 2005 Progress Software Corporation www.progress.com Voice: (781) 280-4000 Fax: (781) 280-4095 |